chore(claude-config): namespace agents and commands under cypher#693
chore(claude-config): namespace agents and commands under cypher#693bhabalan wants to merge 2 commits into
Conversation
- Move .claude/agents/*.md and .claude/commands/*.md under cypher/ subdir - Add description frontmatter to all 8 commands so they show in autocomplete - Update inter-file refs: agent path imports and subagent_type dispatches - Update spec-drift hook user-facing messages to /cypher:spec-drift-changed - Update CLAUDE.md command tables to use /cypher:* invocation names
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9267518de7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ``` | ||
| Task({ | ||
| subagent_type: "ticket-worker", | ||
| subagent_type: "cypher:ticket-worker", |
There was a problem hiding this comment.
When /cypher:fix-tickets reaches the parallel worker launch, this subagent_type does not match any project subagent: Claude Code scans .claude/agents/ recursively but identifies project subagents by their frontmatter name, and .claude/agents/cypher/ticket-worker.md still declares name: ticket-worker rather than cypher:ticket-worker. This means the full lifecycle command will fail to start ticket workers after the namespace move; keep the file path updates, but spawn ticket-worker unless the agent is actually provided as a scoped plugin agent.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in next push. Reverted to subagent_type: "ticket-worker" since project subagents are identified by frontmatter name, not file path. The cypher: prefix only applies to plugin-scoped agents.
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Project subagents are dispatched by frontmatter name, not file path.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 92f63f7292
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| echo "$STAGED_CC" | sed 's/^/ - /' | ||
| echo "" | ||
| echo "Run /spec-drift-changed to validate ai-docs against source code before committing." | ||
| echo "Run /cypher:spec-drift-changed to validate ai-docs against source code before committing." |
There was a problem hiding this comment.
When this hook blocks a git commit with staged packages/contact-center files, it now tells the user to run /cypher:spec-drift-changed. Current Claude Code slash-command docs state that files under .claude/commands/ keep the filename as the command name and subdirectories only appear in the description, so cypher/spec-drift-changed.md is still invoked as /spec-drift-changed, not /cypher:spec-drift-changed. Following the hook's instruction leaves users at an unknown command and they cannot create the verification marker from the blocked flow.
Useful? React with 👍 / 👎.
1 participant
COMPLETES #< INSERT LINK TO ISSUE >
This pull request addresses
< DESCRIBE THE CONTEXT OF THE ISSUE >
by making the following changes
< DESCRIBE YOUR CHANGES >
Change Type
The following scenarios were tested
< ENUMERATE TESTS PERFORMED, WHETHER MANUAL OR AUTOMATED >
The GAI Coding Policy And Copyright Annotation Best Practices
Checklist before merging
Make sure to have followed the contributing guidelines before submitting.